Renamed Element.Create to Element.CreateElementContinue. This naming, while more verbose, is more consistent with the naming conventions used by other "overloaded" functions in the etree package. The Create name was ambiguous, especially considering that there are many other types of tokens that are created using the same verb (CreateAttr, CreateProcInst, etc.).

yeah I waffled on that too - however I would strongly reconsider, as repeating CreateElementContinue 100 times is going to be really painful/ugly for anyone building a tree of any decent size

I'm sympathetic to the verbosity concern, but I'm less flexible on the ambiguity aspect. If we're to use the Create terminology, then it can't be ambiguous about what's being created, especially since none of the existing functions are ambiguous.

Let's try AddElement. There's already an existing function AddToken, so it's not without precedent. Not as short as Create, but not much longer either.

I wish go had function overloading.

another option is "Continue" - but AddElement is short enough that I wont fight you on it